apps/web/src/components/Sidebar.tsx (1)

660-684: Consider extracting shared clipboard+toast flow.

copy-path and copy-thread-id now repeat nearly identical copy/error toast handling. A small helper would reduce drift and keep copy actions consistent.

Refactor sketch

+const copyValueWithToast = async ({
+  value,
+  successTitle,
+  failureTitle,
+}: {
+  value: string;
+  successTitle: string;
+  failureTitle: string;
+}) => {
+  try {
+    await copyTextToClipboard(value);
+    toastManager.add({ type: "success", title: successTitle, description: value });
+  } catch (error) {
+    toastManager.add({
+      type: "error",
+      title: failureTitle,
+      description: error instanceof Error ? error.message : "An error occurred.",
+    });
+  }
+};

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@apps/web/src/components/Sidebar.tsx` around lines 660 - 684, Extract the
repeated clipboard + toast logic into a helper like
copyToClipboardWithToast(text: string, options?: {successTitle?: string,
successDescription?: string, errorTitle?: string}) and use it from the click
handlers for "copy-path" and "copy-thread-id"; move the existing try/catch and
toastManager.add calls into that helper, have it check for empty text (returning
a failure toast similar to the current "Path unavailable"), call
copyTextToClipboard inside the try block, and surface either a success toast
with the provided title/description or an error toast using error instanceof
Error ? error.message : "An error occurred." so both handlers call
copyToClipboardWithToast(threadWorkspacePath, {successTitle: "Path copied"}) and
copyToClipboardWithToast(threadId, {successTitle: "Thread ID copied"})
respectively.